Skip to content

Add textAlign to Paragraph and improve JSDoc#4482

Merged
justinhenricks merged 1 commit into
2026-01from
jh/add-text-align-paragraph-2026-01
May 21, 2026
Merged

Add textAlign to Paragraph and improve JSDoc#4482
justinhenricks merged 1 commit into
2026-01from
jh/add-text-align-paragraph-2026-01

Conversation

@justinhenricks
Copy link
Copy Markdown
Contributor

Backport of #4455 to 2026-01.

TLDR

Add textAlign to ParagraphElementProps and replace the type prop, aligning ui-extensions types with the underlying component change.

What changed

  • Added textAlign prop ('start' | 'end' | 'center' | 'auto') to ParagraphElementProps
  • Removed type prop ('paragraph' | 'small')
  • Improved JSDoc for BaseElementProps, BaseElementPropsWithChildren

@github-actions
Copy link
Copy Markdown
Contributor

🚨🚨🚨 Docs migration in progress 🚨🚨🚨

We are actively migrating UI extension reference docs to MDX in the areas/platforms/shopify-dev zone of the monorepo. This impacts docs for the following surfaces:

During this migration, please be aware of the following:

.doc.ts files are being deprecated. Changes to .doc.ts files in this repo will not be reflected in the new MDX-based docs. If you need to update docs for a reference that has already been migrated, make your changes directly in the areas/platforms/shopify-dev zone of the monorepo instead.

Doc comments in .ts source files (the comment blocks above types and functions) are also affected. Generating docs from these comments currently requires a newer version of the @shopify/generate-docs library that isn't yet available. Updates to doc comments may not produce the expected output until the migration is complete.

Examples that previously lived in this repo are being moved to the areas/platforms/shopify-dev zone of the monorepo and should be authored there going forward.

What should I do?

  • If your PR includes changes to .doc.ts files, doc comments, or examples, please reach out to us in #devtools-proj-templated-refs so we can help ensure your updates are captured correctly.
  • If your PR is limited to source code changes (non-docs), you can ignore this notice.

Thanks for your patience while we complete the migration! 🙏

@justinhenricks justinhenricks requested a review from mcvinci May 20, 2026 21:27
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mcvinci @rennyG can you check if those changes are ok?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep I think this is fine, but it's worth reaching out to our devs to confirm

@justinhenricks justinhenricks merged commit 9b16692 into 2026-01 May 21, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants